Add api version 2018-10-01 for Microsoft.Compute#3896
Add api version 2018-10-01 for Microsoft.Compute#3896jhendrixMSFT merged 1 commit intoAzure:masterfrom
Conversation
Automation for azure-sdk-for-pythonThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-rubyNothing to generate for azure-sdk-for-ruby |
Automation for azure-sdk-for-nodeThe initial PR has been merged into your service PR: |
Automation for azure-sdk-for-javaNothing to generate for azure-sdk-for-java |
Automation for azure-sdk-for-goThe initial PR has been merged into your service PR: |
|
Can one of the admins verify this patch? |
jhendrixMSFT
left a comment
There was a problem hiding this comment.
As a first step please have a look at the linter failures, see the log for more details.
specification/compute/resource-manager/Microsoft.Compute/stable/2018-10-01/gallery.json
Outdated
Show resolved
Hide resolved
Automation for azure-sdk-for-jsNothing to generate for azure-sdk-for-js |
There was a problem hiding this comment.
I am not sure why its showing as "added" even while comparing with Azure repository.. This change in readme.md was simply pulled in from Azure master to forked repository
There was a problem hiding this comment.
Same as other comment. This file came in from Azure master actually to forked repository..
There was a problem hiding this comment.
all changes in this file are already there in Azure master branch.. Not sure why its showing as "added" in my PR, as I simply pulled Azure master into my forked repository.
This checklist is used to make sure that common issues in a pull request are addressed. This will expedite the process of getting your pull request merged and avoid extra work on your part to fix issues discovered during the review process.
PR information
api-versionin the path should match theapi-versionin the spec).Quality of Swagger